SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Web resource</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Web resource</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

<p>A <b>web resource</b> is any identifiable resource (digital, physical, or abstract) present on or connected to the <a href="World_Wide_Web" title="World Wide Web">World Wide Web</a>.<sup id="cite_ref-rfc3986_1-0" class="reference"><a href="#cite_note-rfc3986-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-fielding_dissertation_2-0" class="reference"><a href="#cite_note-fielding_dissertation-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-uri_identify_3-0" class="reference"><a href="#cite_note-uri_identify-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> Resources are identified using <a href="Uniform_Resource_Identifier" title="Uniform Resource Identifier">Uniform Resource Identifiers</a> (URIs).<sup id="cite_ref-rfc3986_1-1" class="reference"><a href="#cite_note-rfc3986-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-rfc1738_4-0" class="reference"><a href="#cite_note-rfc1738-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> In the <a href="Semantic_Web" title="Semantic Web">Semantic Web</a>, web resources and their semantic properties are described using the <a href="Resource_Description_Framework" title="Resource Description Framework">Resource Description Framework</a> (RDF).<sup id="cite_ref-rdf_index_5-0" class="reference"><a href="#cite_note-rdf_index-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>The concept of <i>resource</i> has evolved during the Web's history, from the early notion of static addressable <a href="Electronic_document" title="Electronic document">documents</a> or <a href="Computer_file" title="Computer file">files</a>, to a more generic and abstract definition, now encompassing every "thing" or <a href="https://en.wiktionary.org/wiki/entity" class="extiw external" title="wikt:entity">entity</a> that can be identified, named, addressed or handled, in any way whatsoever, in the web at large, or in any networked information system. The declarative aspects of a resource (identification and naming) and its functional aspects (addressing and technical handling) weren't clearly distinct in the early specifications of the web, and the very definition of the concept has been the subject of long and still open debate involving difficult, and often arcane, technical, social, linguistic and philosophical issues.

</p>

<div class="mw-heading mw-heading2"><h2 id="From_documents_and_files_to_web_resources">From documents and files to web resources</h2></div>

<p>In the early specifications of the web (1990–1994), the term <i>resource</i> is barely used at all. The web is designed as a network of more or less static addressable objects, basically files and documents, linked using <a href="URL" title="URL">Uniform Resource Locators</a> (URLs). A web resource is implicitly defined as something which can be identified. The identification serves two distinct purposes: naming and addressing; the latter only depends on a protocol. It is notable that RFC 1630 does not attempt to define at all the notion of resource; actually it barely uses the term besides its occurrence in Uniform Resource Identifier (URI), Uniform Resource Locator (URL), and Uniform Resource Name (URN), and still speaks about "Objects of the Network".

</p><p>RFC 1738 (December 1994) further specifies URLs, the term "Universal" being changed to "Uniform". The document is making a more systematic use of <i>resource</i> to refer to objects which are "available", or "can be located and accessed" through the internet. There again, the term <i>resource</i> itself is not explicitly defined.

</p>

<div class="mw-heading mw-heading2"><h2 id="From_web_resources_to_abstract_resources">From web resources to abstract resources</h2></div>

<p>The first explicit definition of <i>resource</i> is found in RFC 2396, in August 1998:

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}

/* end https://en.wikipedia.org/ */

</style><blockquote class="templatequote"><p>

A resource can be anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources. Not all resources are network "retrievable"; e.g., human beings, corporations, and bound books in a library can also be considered resources. The resource is the conceptual mapping to an entity or set of entities, not necessarily the entity which corresponds to that mapping at any particular instance in time. Thus, a resource can remain constant even when its content---the entities to which it currently corresponds---changes over time, provided that the conceptual mapping is not changed in the process.</p></blockquote>

<p>Although examples in this document were still limited to physical entities, the definition opened the door to more abstract resources. Providing a concept is given an identity, and this identity is expressed by a well-formed URI (Uniform Resource Identifier, a superset of URLs), then a concept can be a resource as well.

</p><p>In January 2005, RFC 3986 makes this extension of the definition completely explicit:

'…abstract concepts can be resources, such as the operators and operands of a mathematical equation, the types of a relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero, one, and infinity).'

</p>

<div class="mw-heading mw-heading2"><h2 id="Resources_in_RDF_and_the_Semantic_Web">Resources in RDF and the Semantic Web</h2></div>

<p>First released in 1999, RDF was first intended to describe resources, in other words to declare <a href="Metadata" title="Metadata">metadata</a> of resources in a standard way. A RDF description of a resource is a set of triples (subject, predicate, object), where <i>subject</i> represents the resource to be described, <i>predicate</i> a type of property relevant to this resource, and <i>object</i> can be data or another resource. The predicate itself is considered as a resource and identified by a URI. Hence, properties like "title", "author" are represented in RDF as resources, which can be used, in a recursive way, as the subject of other triples.

Building on this recursive principle, RDF vocabularies, such as <a href="RDF_Schema" title="RDF Schema">RDF Schema</a> (RDFS), <a href="Web_Ontology_Language" title="Web Ontology Language">Web Ontology Language</a> (OWL), and <a href="Simple_Knowledge_Organization_System" title="Simple Knowledge Organization System">Simple Knowledge Organization System</a> will pile up definitions of abstract resources such as classes, properties, concepts, all identified by URIs.

</p><p>RDF also specifies the definition of anonymous resources or <a href="Blank_node" title="Blank node">blank nodes</a>, which are not absolutely identified by URIs.

</p>

<div class="mw-heading mw-heading3"><h3 id="Using_HTTP_URIs_to_identify_abstract_resources">Using HTTP URIs to identify abstract resources</h3></div>

<p><a href="URL" title="URL">URLs</a>, particularly <a href="Uniform_resource_identifier" class="mw-redirect" title="Uniform resource identifier">HTTP URIs</a>, are frequently used to identify abstract resources, such as classes, properties or other kind of concepts. Examples can be found in RDFS or OWL <a href="Ontology_(computer_science)" class="mw-redirect" title="Ontology (computer science)">ontologies</a>. Since such URIs are associated with the HTTP protocol, the question arose of which kind of representation, if any, should one get for such resources through this protocol, typically using a web browser, and if the syntax of the URI itself could help to differentiate "abstract" resources from "information" resources. The URI specifications such as RFC 3986 left to the protocol specification the task of defining actions performed on the resources and they do not provide any answer to this question. It had been suggested that an HTTP URI identifying a resource in the original sense, such as a file, document, or any kind of so-called information resource, should be "slash" URIs — in other words, should not contain a <a href="Fragment_identifier" class="mw-redirect" title="Fragment identifier">fragment identifier</a>, whereas a URI used to identify a concept or abstract resource should be a "hash" URI using a fragment identifier.

</p><p>For example: <code>http://www.example.org/catalogue/widgets.html</code> would both identify and locate a web page (maybe providing some human-readable description of the widgets sold by Silly Widgets, Inc.) whereas <code>http://www.example.org/ontology#Widget</code> would identify the abstract concept or class "Widget" in this company ontology, and would not necessarily retrieve any physical resource through <a href="HTTP_protocol" class="mw-redirect" title="HTTP protocol">HTTP protocol</a>. But it has been answered that such a distinction is impossible to enforce in practice, and famous standard vocabularies provide counter-examples widely used. For example, the <a href="Dublin_Core" title="Dublin Core">Dublin Core</a> concepts such as "title", "publisher", "creator" are identified by "slash" URIs like <code>http://purl.org/dc/elements/1.1/title</code>.

</p><p>The general question of which kind of resources HTTP URI should or should not identify has been formerly known in W3C as the <a rel="nofollow" class="external text" href="http://www.w3.org/2001/tag/issues.html#httpRange-14">httpRange-14</a> issue, following its name on the list defined by the (TAG). The TAG delivered in 2005 a final answer to this issue, making the distinction between an "information resource" and a "non-information" resource dependent on the type of answer given by the server to a "GET" request:

</p>

<ul><li><a href="HTTP_200" class="mw-redirect" title="HTTP 200">2xx Success</a> indicates resource is an information resource.</li>

<li><a href="HTTP_303" title="HTTP 303">303 See Other</a> indicates the resource could be informational or abstract; the redirection target could tell you.</li>

<li><a href="List_of_HTTP_status_codes#4xx_client_errors" title="List of HTTP status codes">4xx Client Error</a> provides no information at all.</li></ul>

<p>This allows vocabularies (like <a href="Dublin_Core" title="Dublin Core">Dublin Core</a>, <a href="FOAF" title="FOAF">FOAF</a>, and <a href="Wordnet" class="mw-redirect" title="Wordnet">Wordnet</a>) to continue to use slash instead of hash for pragmatic reasons. While this compromise seems to have met a consensus in the Semantic Web community, some of its prominent members such as <a href="Patrick_J._Hayes" class="mw-redirect" title="Patrick J. Hayes">Pat Hayes</a> have expressed concerns both on its technical feasibility and conceptual foundation. According to Patrick Hayes' viewpoint, the very distinction between "information resource" and "other resource" is impossible to find and should better not be specified at all, and <a href="Ambiguity" title="Ambiguity">ambiguity</a> of the referent resource is inherent to URIs like to any naming mechanism.

</p>

<div class="mw-heading mw-heading3"><h3 id="Resource_ownership,_intellectual_property_and_trust">Resource ownership, intellectual property and trust</h3></div>

<p>In RDF, "anybody can declare anything about anything". Resources are defined by formal descriptions which anyone can publish, copy, modify and publish over the web. If the content of a web resource in the classical sense (a web page or on-line file) is clearly owned by its publisher, who can claim intellectual property on it, an abstract resource can be defined by an accumulation of RDF descriptions, not necessarily controlled by a unique publisher, and not necessarily consistent with each other. It's an open issue to know if a resource should have an authoritative definition with clear and trustable ownership, and in this case, how to make this description technically distinct from other descriptions. A parallel issue is how intellectual property may apply to such descriptions.

</p>

<ul><li><a href="Address_bar" title="Address bar">Address bar</a></li>

<li><a href="Resource_(computer_science)" class="mw-redirect" title="Resource (computer science)">Resource (computer science)</a></li>

<li><a href="Resource-oriented_architecture" title="Resource-oriented architecture">Resource-oriented architecture</a> (ROA)</li>

<li><a href="Resource-oriented_computing" title="Resource-oriented computing">Resource-oriented computing</a> (ROC)</li>

<li><a href="Representational_state_transfer" class="mw-redirect" title="Representational state transfer">Representational state transfer</a> (REST)</li>

<li><a href="Web_service" title="Web service">Web service</a> and <a href="Service-oriented_architecture" title="Service-oriented architecture">Service-oriented architecture</a> (SOA)</li>

<li><a href="Web-oriented_architecture" title="Web-oriented architecture">Web-oriented architecture</a> (WOA)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Citations">Citations</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-rfc3986-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-rfc3986_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-rfc3986_1-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc3986">RFC 3986 Uniform Resource Identifier (URI): Generic Syntax</a></span>

</li>

<li id="cite_note-fielding_dissertation-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-fielding_dissertation_2-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm">Roy T. Fielding's Dissertation</a></span>

</li>

<li id="cite_note-uri_identify-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-uri_identify_3-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.w3.org/DesignIssues/HTTP-URI.html">What do HTTP URIs Identify?</a>, by <a href="Tim_Berners-Lee" title="Tim Berners-Lee">Tim Berners-Lee</a></span>

</li>

<li id="cite_note-rfc1738-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-rfc1738_4-0">^</a></b></span> <span class="reference-text">RFC 1738 Uniform Resource Locators (URL)</span>

</li>

<li id="cite_note-rdf_index-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-rdf_index_5-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://www.w3.org/standards/techs/rdf">RDF Current Status</a></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading3"><h3 id="Sources">Sources</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .refbegin{margin-bottom:0.5em}.mw-parser-output .refbegin-hanging-indents>ul{margin-left:0}.mw-parser-output .refbegin-hanging-indents>ul>li{margin-left:0;padding-left:3.2em;text-indent:-3.2em}.mw-parser-output .refbegin-hanging-indents ul,.mw-parser-output .refbegin-hanging-indents ul li{list-style:none}@media(max-width:720px){.mw-parser-output .refbegin-hanging-indents>ul>li{padding-left:1.6em;text-indent:-1.6em}}.mw-parser-output .refbegin-columns{margin-top:0.3em}.mw-parser-output .refbegin-columns ul{margin-top:0}.mw-parser-output .refbegin-columns li{page-break-inside:avoid;break-inside:avoid-column}@media screen{.mw-parser-output .refbegin{font-size:90%}}

/* end https://en.wikipedia.org/ */

</style><div class="refbegin" style="">

<ul><li><a rel="nofollow" class="external text" href="http://www.w3.org/1999/05/WCA-terms/">Web Characterization Terminology & Definitions Sheet</a>, editors: Brian Lavoie and Henrik Frystyk Nielsen, May 1999.</li>

<li><a rel="nofollow" class="external text" href="http://www.w3.org/DesignIssues/TermResource.html">A Short History of "Resource" in web architecture.</a>, by <a href="Tim_Berners-Lee" title="Tim Berners-Lee">Tim Berners-Lee</a></li>

<li>Presentations at <a rel="nofollow" class="external text" href="http://www.ibiblio.org/hhalpin/irw2006/">IRW 2006 conference</a>, <a rel="nofollow" class="external text" href="http://webtechmag.com/">Web resources</a>

<ul><li><a rel="nofollow" class="external text" href="http://www.w3.org/2006/04/irw65/urisym.html">A Pragmatic Theory of Reference for the Web</a>, by <a href="Dan_Connolly_(computer_scientist)" title="Dan Connolly (computer scientist)">Dan Connolly</a>.</li>

<li><a rel="nofollow" class="external text" href="http://www.ibiblio.org/hhalpin/irw2006/presentations/HayesSlides.pdf">In Defense of Ambiguity</a>, by <a href="Patrick_J._Hayes" class="mw-redirect" title="Patrick J. Hayes">Patrick Hayes</a>.</li></ul></li>

<li><a rel="nofollow" class="external text" href="http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS//Vol-201/43.pdf">Towards an OWL ontology for identity on the web</a>, by Valentina Presutti and Aldo Gangemi, <a rel="nofollow" class="external text" href="http://swapconf.it/2006/">SWAP2006 conference</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20061224214413/http://www.swapconf.it/2006/">Archived</a> 2006-12-24 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>.</li></ul>

</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Web_interfaces26" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Web_interfaces26" style="font-size:114%;margin:0 4em"><a href="Web_API" title="Web API">Web interfaces</a></div></th></tr><tr><td colspan="2" class="navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold"><div id="Server-side154"><a href="Server-side" class="mw-redirect" title="Server-side">Server-side</a></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Communication_protocol" title="Communication protocol">Protocols</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="HTTPS" title="HTTPS">Encryption</a></li>

<li><a href="WebDAV" title="WebDAV">WebDAV</a></li></ul></li>

<li><a href="WebSocket" title="WebSocket">WebSocket</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Server_application_programming_interface" title="Server application programming interface">Server APIs</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Netscape_Server_Application_Programming_Interface" title="Netscape Server Application Programming Interface">C NSAPI</a></li>

<li><a href="Apache_HTTP_Server#Feature_overview" title="Apache HTTP Server">C ASAPI</a></li>

<li><a href="Internet_Server_Application_Programming_Interface" title="Internet Server Application Programming Interface">C ISAPI</a></li>

<li><a href="Jakarta_Servlet" title="Jakarta Servlet">Jakarta Servlet</a>

<ul><li><a href="Web_container" title="Web container">container</a></li></ul></li>

<li><a href="HTTP_handler" title="HTTP handler">ASP.NET Handler</a></li>

<li><a href="Web_Server_Gateway_Interface" title="Web Server Gateway Interface">Python WSGI</a></li>

<li><a href="Asynchronous_Server_Gateway_Interface" title="Asynchronous Server Gateway Interface">Python ASGI</a></li>

<li><a href="JSGI" title="JSGI">JavaScript JSGI</a></li>

<li><a href="Java_Portlet_Specification" title="Java Portlet Specification">Portlet</a>

<ul><li><a href="Java_Portlet_Specification" title="Java Portlet Specification">container</a></li></ul></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="List_of_Apache_modules" title="List of Apache modules">Apache modules</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Server_Side_Includes" title="Server Side Includes">mod_include</a></li>

<li><a href="Mod_parrot" class="mw-redirect" title="Mod parrot">mod_parrot</a></li>

<li><a href="Mod_proxy" title="Mod proxy">mod_proxy</a></li>

<li><a href="Mod_python" title="Mod python">mod_python</a></li>

<li><a href="Phusion_Passenger" title="Phusion Passenger">Phusion Passenger</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Topics</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Web_service" title="Web service">Web service</a> vs. </li>

<li><a href="Webhook" title="Webhook">Webhook</a></li>

<li><a href="Application_server" title="Application server">Application server</a>

<ul><li><a href="List_of_application_servers" title="List of application servers">comparison</a></li></ul></li>

<li><a href="Server-side_scripting" title="Server-side scripting">Scripting</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><td colspan="2" class="navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold"><div id="Client-side89"><a href="Client-side" class="mw-redirect" title="Client-side">Client-side</a></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Plug-in_(computing)" title="Plug-in (computing)">Browser APIs</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="NPAPI" title="NPAPI">C NPAPI</a>

<ul><li><a href="NPAPI#LiveConnect" title="NPAPI">LiveConnect</a></li>

<li><a href="NPAPI#XPConnect" title="NPAPI">XPConnect</a></li></ul></li>

<li><a href="NPAPI#NPRuntime" title="NPAPI">C NPRuntime</a></li>

<li><a href="Google_Native_Client#Pepper" title="Google Native Client">C PPAPI</a>

<li><a href="ActiveX" title="ActiveX">ActiveX</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Web_API#Client_side" title="Web API">Web APIs</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="WHATWG" title="WHATWG">WHATWG</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="HTML_audio" title="HTML audio">Audio</a></li>

<li><a href="Canvas_element" title="Canvas element">Canvas</a></li>

<li><a href="HTML_video" title="HTML video">Video</a></li>

<li><a href="WebSocket" title="WebSocket">WebSockets</a></li>

<li><a href="Web_Messaging" title="Web Messaging">Web messaging</a></li>

<li><a href="Web_storage" title="Web storage">Web storage</a></li>

<li><a href="Web_worker" title="Web worker">Web worker</a></li>

<li><a href="XMLHttpRequest" title="XMLHttpRequest">XMLHttpRequest</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="World_Wide_Web_Consortium" title="World Wide Web Consortium">W3C</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="DOM_event" title="DOM event">DOM events</a></li>

<li><a href="W3C_Geolocation_API" title="W3C Geolocation API">Geolocation</a></li>

<li><a href="Indexed_Database_API" title="Indexed Database API">IndexedDB</a></li>

<li><a href="WebAssembly" title="WebAssembly">WebAssembly</a></li>

<li><a href="WebAuthn" title="WebAuthn">WebAuthn</a></li>

<li><a href="WebGPU" title="WebGPU">WebGPU</a></li>

<li><a href="WebRTC" title="WebRTC">WebRTC</a></li>

<li><a href="WebXR" title="WebXR">WebXR</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Khronos_Group" title="Khronos Group">Khronos</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="WebCL" title="WebCL">WebCL</a></li>

<li><a href="WebGL" title="WebGL">WebGL</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Others</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Gears_(software)" title="Gears (software)">Gears</a></li>

<li><a href="Web_SQL_Database" title="Web SQL Database">Web SQL Database</a> (formerly W3C)</li>

<li><a href="WebUSB" title="WebUSB">WebUSB</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Topics</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Ajax_(programming)" title="Ajax (programming)">Ajax</a> and <a href="Remote_scripting" title="Remote scripting">Remote scripting</a> vs. <a href="Dynamic_HTML" title="Dynamic HTML">DHTML</a></li>

<li><a href="Browser_extension" title="Browser extension">Browser extension</a></li>

<li><a href="Cross-site_scripting" title="Cross-site scripting">Cross-site scripting</a> and <a href="Cross-origin_resource_sharing" title="Cross-origin resource sharing">CORS</a></li>

<li><a href="Hydration_(web_development)" title="Hydration (web development)">Hydration</a></li>

<li><a href="Mashup_(web_application_hybrid)" title="Mashup (web application hybrid)">Mashup</a></li>

<li><a href="Client-side_persistent_data" title="Client-side persistent data">Persistent data</a></li>

<li><a href="Dynamic_web_page#Client-side_scripting" title="Dynamic web page">Scripting</a></li></ul>

<ul><li><a href="Frontend_and_backend" title="Frontend and backend">Frontend and backend</a></li>

<li><a href="Microservices" title="Microservices">Microservices</a>

<li><a href="GraphQL" title="GraphQL">GraphQL</a></li></ul></li>

<li><a href="Push_technology" title="Push technology">Push technology</a></li>

<li><a href="Solution_stack" title="Solution stack">Solution stack</a></li>

<ul><li><a href="Static_web_page" title="Static web page">Static</a></li>

<li><a href="Dynamic_web_page" title="Dynamic web page">Dynamic</a></li></ul></li>

<li><a href="Web_standards" title="Web standards">Web standards</a></li>

<li><a href="Web_API_security" title="Web API security">Web API security</a></li>

<li><a href="Web_application" title="Web application">Web application</a>

<li><a href="Single-page_application" title="Single-page application">Single-page</a></li>

<li><a href="Progressive_web_app" title="Progressive web app">Progressive</a></li></ul></li>

<li><a href="Web_framework" title="Web framework">Web framework</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-24" href="https://en.wikipedia.org/wiki/?title=Web_resource&oldid=1302290866">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>